refactor: return Blake2b256 for block and TX hash #974
+88
−120
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This switches from returning the string representation of a block/TX hash to the underlying Blake2b256 type containing the hash bytes. Those bytes are used all over the place, and it's cumbersome to need to use hex.DecodeString() everywhere to convert back to bytes Signed-off-by: Aurora Gaffney <[email protected]>
wolf31o2
approved these changes
Apr 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This switches from returning the string representation of a block/TX hash to the underlying Blake2b256 type containing the hash bytes. Those bytes are used all over the place, and it's cumbersome to need to use hex.DecodeString() everywhere to convert back to bytes
BREAKING CHANGE: library consumers will need to convert from bytes to string before use